Computing devices for sending and receiving configuration information

ABSTRACT

A computing device configured for sending configuration information is described. The computing device includes a processor and instructions stored in memory that is in electronic communication with the processor. The computing device obtains access information. The computing device further generates a graphic based on the access information. The computing device also receives a configuration information request associated with the graphic. Additionally, the computing device sends the configuration information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 13/790,353, entitled “Computing Devices for Sending and ReceivingConfiguration Information,” filed Mar. 8, 2013, the disclosure of whichis incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to computer andcomputer-related technology. More specifically, the present disclosurerelates to computing devices for sending and receiving configurationinformation.

BACKGROUND

The use of electronic devices has become increasingly prevalent inmodern society. As the cost of electronic devices has declined and asthe usefulness of electronic devices has increased, people are usingthem for a wide variety of purposes. For example, many people useelectronic devices to perform work tasks as well as to seekentertainment. One type of an electronic device is a computer.

Computer technologies continue to advance at a rapid pace. Computerscommonly used include everything from hand-held computing devices tolarge multi-processor computer systems. These computers includesoftware, such as applications including user interfaces, in order tomake them useful and accessible to an end user. Computers areincreasingly linked with other computers through networks. With theexpansion of computer technology, the size of networks has continued toincrease. Networks may link computers together that are a great distanceapart.

One of the challenges with large networks is configuring the electronicdevices that are connected to the network. For example, electronicdevices that are not properly configured may not be able to communicateinformation via the network. In some cases, the challenges associatedwith improperly configured electronic devices may result in errorsthroughout the network. As can be observed from this discussion, systemsand methods that assist in configuration over a network may bebeneficial.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating one configuration of computingdevices in which systems and methods for sending and receivingconfiguration information may be implemented;

FIG. 2 is a flow diagram illustrating one configuration of a method forsending configuration information by a computing device;

FIG. 3 is a flow diagram illustrating one configuration of a method forreceiving configuration information by a computing device;

FIG. 4 is a block diagram that illustrates another configuration ofcomputing devices in which systems and methods for sending and receivingconfiguration information may be implemented;

FIG. 5 is a flow diagram illustrating another configuration of a methodfor sending configuration information by a computing device;

FIG. 6 is a flow diagram illustrating another configuration of a methodfor receiving configuration information by a computing device;

FIG. 7 is a thread diagram illustrating one configuration of a methodfor sending and receiving configuration information by computingdevices;

FIG. 8 is a block diagram that illustrates another configuration ofcomputing devices in which systems and methods for sending and receivingconfiguration information may be implemented;

FIG. 9 is a block diagram that illustrates one configuration of anetwork where systems and methods for sending and receivingconfiguration information may be implemented; and

FIG. 10 illustrates various components that may be utilized on acomputing device.

DETAILED DESCRIPTION

A computing device configured for sending configuration information isdescribed. The computing device includes a processor and instructionsstored in memory that is in electronic communication with the processor.The computing device obtains access information. The computing devicealso generates a graphic based on the access information. The computingdevice also receives a configuration information request associated withthe graphic. Furthermore, the computing device sends the configurationinformation.

Generating the graphic based on the access information may includeencoding the access information into the graphic. The computing devicemay secure the configuration information to produce securedconfiguration information. The computing device may receiveauthentication information. The computing device may send an inventorydata request and receive inventory data.

The access information may include an authentication informationrequest, a network connectivity module, a digital certificate, accessidentification information, a connecting prompt and/or a scanningmodule. The configuration information may include an authenticationrule, configuration identification information, a policy, anapplication, a setting, a request for inventory data, an implementationinstruction and/or a configuration prompt.

A computing device configured for receiving configuration information isalso described. The computing device includes a processor andinstructions stored in memory that is in electronic communication withthe processor. The computing device scans a graphic. The computingdevice also extracts access information based on the graphic. Thecomputing device also applies access information to one or morecommunications settings. The computing device further sends aconfiguration information request associated with the graphic. Thecomputing device additionally receives the configuration information.

The computing device may receive a graphic reader that decodes theaccess information. The computing device may determine inventory dataand send inventory data.

The configuration information may be secured configuration information.The computing device may receive a security module that interprets thesecured configuration information. The access information may include anauthentication information request. The computing device may sendauthentication information.

A method for sending configuration information by a computing device isalso described. The method includes obtaining access information. Themethod additionally includes generating a graphic based on the accessinformation. The method also includes receiving a configurationinformation request associated with the graphic. The method furtherincludes sending the configuration information.

A method for receiving configuration information by a computing deviceis also described. The method includes scanning a graphic. The methodalso includes extracting access information based on the graphic. Themethod also includes applying access information to one or morecommunications settings. The method also includes sending aconfiguration information request associated with the graphic. Themethod further includes receiving the configuration information.

The systems and methods disclosed herein describe computing devices forsending and receiving configuration information. In some approaches, amobile device (e.g., a pad or tablet device) may utilize a camera toconfigure itself from a readable graphic like a barcode. For example,the graphic may include settings for a Wi-Fi (e.g., Institute ofElectrical and Electronics Engineers (IEEE) 802.11) configuration forthe device. In some approaches, a pad or tablet device manufacturer mayplace an application on the device in the factory to simplify the stepsfor configuring device settings (e.g., the Wi-Fi configuration). Thesystems and methods disclosed herein may utilize a machine-producedgraphic (e.g., a Quick Response (QR) barcode) as an input fordesignating the configuration settings. This may enable a new device tobe configured by a user with limited time or understanding of the stepsfor set up and configuration. In some approaches, the systems andmethods disclosed herein may be implemented with an administrativesystem management suite.

One example of the systems and methods disclosed herein is given asfollows. In this example, a device copies a secure communicationsapplication, a barcode application and a Wi-Fi configurationapplication, along with a user interface, to the memory of the device.The device may then be packaged and shipped to an end user. A plug-in ona management console may create a barcode containing Wi-Fi configurationinformation, a unique certificate and/or core server information, etc.,and may provide the barcode to an end user. In some approaches, policiesand/or applications may be designated (based on administrator input, forexample) to be pushed to the device (e.g., tablet) upon connection. Inone example, the tablet starts and application(s) to configure the Wi-Fiare initiated. The barcode scanner of the device (e.g., tablet) scansthe barcode containing the Wi-Fi configuration, connects to a networkand provides credentials. Then, the core server or a directory serviceauthenticates the tablet, and the tablet connects to the core serverbased on the information provided. The core server then pushes policiesand applications to the device and retrieves inventory data.

Various configurations of the systems and methods are now described withreference to the Figures, where like reference numbers may indicateidentical or functionally similar elements. The configurations of thepresent systems and methods, as generally described and illustrated inthe Figures herein, could be arranged and designed in a wide variety ofdifferent configurations. Thus, the following more detailed descriptionof several configurations, as represented in the Figures, is notintended to limit the scope of the systems and methods, as claimed, butis merely representative of the various configurations of the systemsand methods.

FIG. 1 is a block diagram that illustrates one configuration ofcomputing devices 102, 104 in which systems and methods for sending andreceiving configuration information may be implemented. Examples ofcomputing device A 102 and/or computing device B 104 include, but arenot limited to, desktop computers, laptop computers, servers,supercomputers, tablet devices, cellular phones, smartphones, gamingsystems and any other computing device. It should be noted that whileFIG. 1 depicts two computing devices 102, 104, the systems and methodsdisclosed herein may be applied to any number of computing devices 102,104. Computing device A 102 may include storage device A 116, an encoder106, a request receiver 108, access information 110, configurationinformation A 112 and/or communications module A 114. In an alternativeimplementation, storage device A 116 may be separate from and coupled tocomputing device A 102. Computing device B 104 may include storagedevice B 130, a graphic scanner 120, a request generator 122, a graphicreader 124, configuration information B 132 and/or a communicationsmodule B 126. In an alternative implementation, storage device B 130 maybe separate from and coupled to computing device B 104. Communicationsmodule B 126 may include one or more communications settings 128. Insome instances, computing device A 102 may communicate with computingdevice B 104 via a network 118.

It should be noted that one or more of the elements depicted as includedwithin computing device A 102 and/or computing device B 104 may beimplemented in hardware, software or a combination of both. For example,the encoder 106 may be implemented in hardware, software or acombination of both.

The encoder 106 may create a graphic that includes information. In someimplementations, computing device B 104 may read (e.g., scan, capture,process, etc.) the graphic in order to retrieve the information includedin the graphic. For instance, the encoder 106 may generate a graphicthat contains Wi-Fi configuration information. In this case, computingdevice B 104 may read the graphic in order to retrieve and utilize theWi-Fi configuration information. Once the graphic is read, computingdevice B 104 may access the Wi-Fi configuration informationautomatically. The encoder 106 may store information to the graphicusing any number of encoding protocols. Thus different computing devicesmay retrieve different information from the graphic depending on thedecoding protocol used by the computing devices. Examples of graphicsinclude, but are not limited to, linear barcodes, stacked barcodes,matrix barcodes, QR codes, micro QR codes, artistic QR codes and highcapacity color barcodes.

The encoder 106 may encode information into a graphic. The encoder 106may also provide the graphic to be distributed to computing device B104. In some approaches, the encoder 106 may provide the graphic to aprinter to be produced in a tangible medium. The encoder 106 may alsoprovide the graphic to communications module A 114 for transmission toanother device, for example through email or displayed on a web page.

In an alternative implementation not illustrated in FIG. 1, the encoder106 may be included in another computing device (not illustrated inFIG. 1) that sends the generated graphic to computing device A 102. Forinstance, a management console may include the encoder 106 that encodesthe access information 110 to a digital graphic. In this example, theaccess information 110 incorporated into the graphic may also beincluded on the management console. After the digital graphic has beengenerated, the management console may send the graphic to computingdevice A 102 (e.g., an administrative server) to be distributed. In someimplementations, the management console may obtain a plug-in thatpermits the encoder 106 to generate a graphic. This plug-in may beprovided by computing device A 102 (e.g., the administrative serverdescribed earlier).

The graphic created by the encoder 106 may be based on accessinformation 110. Access information 110 may include one or more piecesof information that allow communication with computing device A 102and/or the network 118. Upon reception, the access information 110 maythen enable computing device B 104 to communicate with computing deviceA 102 and/or the network 118. For example, the access information 110may include the Service Set Identifier (SSID) (e.g., Institute ofElectrical and Electronics Engineers (IEEE) 802.11) and passkey of thenetwork 118. Upon input of the SSID and passkey, computing device B 104may be granted access to the network 118. In another example, the accessinformation 110 may include the Internet Protocol (IP) address ofcomputing device A 102, (e.g., a server). Similarly, upon input of theIP address, computing device B 104 may be granted access to computingdevice A 102 and/or the network 118.

The access information 110 may be input into computing device B 104. Forexample, computing device B 104 may receive input of the SSID andpasskey of the network 118. Alternatively, computing device B 104 mayimplement the access information 110 without any input. For example,computing device B 104 may automatically be granted access tocommunicate with computing device A 102 and/or the network 118 after theaccess information 110 (e.g., the SSID and passkey) has been extractedfrom the graphic. The access information 110 may include accesslimitations imposed on computing device B 104. For example, the accessinformation 110 may indicate the devices of the network 118 thatcomputing device B 104 may contact. Other examples of access information110 will be described in greater detail below.

Configuration information A 112 may be utilized to configure computingdevice B 104. For example, configuration information A 112 may includedevice network settings that allow computing device B 104 to communicatewith other devices via the network 118. In this example, asconfiguration information A 112 is received, computing device B's 104network settings are changed such that it may communicate with otherdevices on the network 118. Configuration information A 112 may includeconfiguration information for a number of devices. For example,computing device A 102 may be a network administrative server andconfiguration information A 112 may include configuration informationfor all the devices on the network 118. Examples of configurationinformation A 112 include, but are not limited to, data, networkconnectivity settings, internet protocols, communication protocols,policies and applications. Other examples of configuration informationwill be described in greater detail below.

Communications module A 114 allows computing device A 102 to communicatewith other computing devices on the network 118. For example,communications module A 114 may send configuration information A 112 tocomputing device B 104. Communications module A 114 may set standardsfor communication between computing device A 102 and computing device B104. Communications module A 114 may also include certain restrictionson communications. For example, communications module A 114 may limitwhat types of files may be transferred to/from computing device A 102.For example, it may be impermissible to transfer executable files.

The request receiver 108 receives requests for configuration informationfrom other computing devices. For example, the request receiver 108 mayprocess a request from computing device B 104 to send configurationinformation B 132 to computing device B 104.

The request received by the request receiver 108 may include informationrelating to the device that sent the request. For example, a requestfrom computing device B 104 may include the IP address and a number ofcharacteristics of computing device B 104. Based on the request, therequest receiver 108 may then determine related configurationinformation A 112. For example, upon reception of a request, the requestreceiver 108 may determine that computing device B's 104 networkprotocol is not current. The request receiver 108 may then includeconfiguration information A 112 relating to a network protocol update.Similarly, the request receiver 108 may determine that configurationinformation pertaining to updates in one of computing device B's 104software applications is not necessary, and as a result does not includeconfiguration information A 112 related to the software application.Thus, based on a particular request, the request receiver 108 maydetermine what portion of configuration information A 112 applies tocomputing device B 104.

Additionally or alternatively, the request receiver 108 may determinepertinent configuration information A 112 based on input. For example,computing device B 104 may request configuration information A 112relating to network connectivity, but may not request configurationinformation A 112 relating to a software application update. In thisexample, the request receiver 108 may include configuration informationA 112 relating to network connectivity, but not include configurationinformation A 112 relating to the software application update.

In some implementations, the request receiver 108 may requireauthentication information before processing a request. Examples ofauthentication information include, but are not limited to, username,password, biometric information, IP address, Media Access Control (MAC)address and device name verification.

Computing device A 102 may send all or part of configuration informationA 112 to computing device B 104. Computing device B 104 may receiveconfiguration information B 132 (which may be all or part ofconfiguration information A 112, for example) from computing device A102. In some implementations, computing device A 102 may be anadministrative server that receives configuration information A 112 fromanother computing device (not shown in FIG. 1). In this example, theadministrative server may receive configuration information A 112 fromthe other computing device and relay all or part of configurationinformation A 112 to computing device B 104. In some implementations,this other computing device may be termed a management console and/ormay access a management console on computing device A 102 that managesother computing devices (e.g., computing device B 104).

Examples of storage device A 116 include hard disks, flash memory,dynamic random access memory (DRAM), static random access memory (SRAM),floppy disks, magnetic tapes, optical disks and any other data storagemedium. Examples of configurations of storage device A 116 includedirect-attached storage (DAS), storage area network (SAN) andnetwork-attached storage (NAS), etc.

According to an example, storage device A 116 may be connected tocomputing device A 102. Examples of connections include, but are notlimited to, a Universal Serial Bus (USB) connection, Ethernetconnection, connection through an intervening computing device (e.g., aserver) and connection through a network. For instance, storage device A116 may be directly connected to computing device A 102.

It should be noted that in some configurations (not shown in FIG. 1),computing device A 102 may be coupled to storage device A 116 through anintervening computing device (e.g., a server, a desktop computer, etc.).For example, computing device A 102 may not be directly connected tostorage device A 116, but may access storage device A 116 bycommunicating with the intervening computing device. For instance, theintervening computing device may host storage device A 116. Accordingly,the systems and methods disclosed herein may be applied to function inconjunction with the intervening computing device.

Computing device A 102 may be coupled to computing device B 104 througha network 118. Examples of a network 118 include personal area networks,local area networks (LAN), wide area networks (WAN), cellular networksand any other type of network.

The graphic scanner 120 records and stores the graphic to computingdevice B 104. For example, the graphic scanner 120 (e.g., camera of asmartphone) may take a picture of a QR code and store the graphic tostorage device B 130. If the graphic is printed on a physical medium,the graphic scanner 120 may convert the physical graphic into a digitalgraphic. Examples of graphic scanners 120 include, but are not limitedto, cameras, lasers, light sources, charge-coupled device (CCD)scanners, and contact image sensor (CIS) scanners.

A graphic reader 124 may be coupled to the graphic scanner 120. Thegraphic reader 124 may extract the information stored within thegraphic. For example, a graphic reader 124 may extract the accessinformation 110 (e.g., a Uniform Resource Locator (URL)) that isembedded in a QR code that was scanned by a graphic scanner 120 (e.g., asmartphone camera). The graphic reader 124 may employ any number ofdecoding protocols to extract the information. For example, a QR codemay include information that is numerically encoded, alphanumericallyencoded, byte encoded, and/or kanji encoded.

The request generator 122 may send a request to computing device A 102to obtain configuration information B 132. The request sent by therequest generator 122 may include information relating to computingdevice B 104. The request generator 122 may base the request on thecharacteristics of computing device B 104. For example, the requestgenerator 122 may request an update to an old version of a softwareapplication on computing device B 104. The request generator 122 mayalso base the request on input. In this example, computing device B 104may request an update to its network drivers.

Computing device B 104 may also include communications module B 126 thatallows computing device B 104 to communicate with computing device A 102and/or the network 118. Communications settings 128 withincommunications module B 126 may establish the procedure by whichcomputing device B 104 communicates with computing device A 102 and/orthe network 118. For example, the communications settings 128 mayindicate protocols for communications between computing device A 102and/or the network 118. Examples of the communications settings 128include SSID settings, passkeys, protocols, version information,encryption protocols, authentication protocols, and/or formattingrequirements, etc. In one example, the access information 110 includedin a graphic and extracted by the graphic reader 124 indicatescommunication settings 128 that will allow computing device B 104 tocommunicate with computing device A 102 and/or the network 118.

As a result of the request, computing device B 104 may receiveconfiguration information B 132. Configuration information B 132 mayrepresent information that establishes device settings related tocomputing device B 104. For example, configuration information B 132 mayinclude device network settings that allow communication betweencomputing device B 104 and other devices on the network 118 (e.g.,computing device A 102). In some approaches, configuration information B132 may constitute a portion of configuration information A 112. Forexample, as described above configuration information A 112 may includeconfiguration information for all computing devices on the network 118.Configuration information B 132 may include that portion ofconfiguration information A 112 that pertains to computing device B 104,and may exclude that portion of configuration information A 112 thatpertains to other computing devices on the network 118. Examples ofconfiguration information B 132 include, but are not limited to networkconnectivity settings, internet protocols, communication protocols,computing policies and applications. Other examples of configurationinformation will be described in greater detail below.

Computing device B 104 may include storage device B 130. Examples ofstorage device B 130 include hard disks, flash memory, dynamic randomaccess memory (DRAM), static random access memory (SRAM), floppy disks,magnetic tapes, optical disks and any other data storage medium.Examples of configurations of storage device B 130 includedirect-attached storage (DAS), storage area network (SAN) andnetwork-attached storage (NAS), etc.

According to an example, storage device B 130 may be connected tocomputing device B 104. Examples of connections include, but are notlimited to, a USB connection, Ethernet connection, connection through anintervening computing device (e.g., a server) and connection through anetwork. For instance, storage device B 130 may be directly connected tocomputing device B 104.

It should be noted that in some configurations (not shown in FIG. 1),computing device B 104 may be coupled to storage device B 130 through anintervening computing device (e.g., a server, a desktop computer, etc.).For example, computing device B 104 may not be directly connected tostorage device B 130, but may access storage device B 130 bycommunicating with the intervening computing device. For instance, theintervening computing device may host storage device B 130. Accordingly,the systems and methods disclosed herein may be applied to function inconjunction with the intervening computing device.

FIG. 2 is a flow diagram illustrating one configuration of a method 200for sending configuration information by a computing device. Computingdevice A 102 obtains 202 access information 110. As described above, theaccess information 110 may include one or more pieces of informationthat allows communication between computing devices on the network 118.An example of access information 110 is the SSID and passkey to thenetwork 118. In this example, computing device A 102 may obtain the SSIDand passkey from the network 118.

In some implementations, computing device A 102 may obtain 202 theaccess information 110 from another computing device. In this example,the other computing device sends the access information 110 to computingdevice A 102. In some implementations, this other computing device maybe termed a management console and/or may access a management console oncomputing device A 102 that manages other computing devices (e.g.,computing device B 104). The other computing device may obtain a plug-inmodule that creates the access information 110. The plug-in module maybe obtained from computing device A 102 (e.g., an administrativeserver). The access information 110 may also be obtained from a networkadministrator. In another implementation computing device A 102generates the access information 110.

The encoder 106 may generate 204 a graphic based on the accessinformation 110. The access information 110 may be embedded in thegraphic. For example, the graphic may include the SSID and passkeynecessary to access the network 118. In one example, the graphic mayinclude a portion of the access information 110. For example, the SSIDof the network 118 may be embedded in the graphic. In this example, thepasskey may be obtained by other means. Accessing the SSID and thepasskey individually increases the security of the transfer of theaccess information 110. Examples of graphics include, but are notlimited to, linear barcodes, stacked barcodes, matrix barcodes, QRcodes, micro QR codes, artistic QR codes and high capacity colorbarcodes.

Different formats of the access information 110 may be encoded to agraphic. For example, numeric access information 110 and/or alphanumericaccess information 110 may be included within a graphic. In someimplementations, access information 110 with differing formats may beencoded into a graphic. For example, numeric access information 110 andalphanumeric access information 110 may be included within a graphic.

In some implementations, computing device A 102 may perform additionalor alternative operations in order to secure communications. Forexample, computing device A 102 may encrypt the access information 110to be embedded in the graphic. Computing device A 102 may use any numberof encryption techniques to secure the access information 110.

According to some approaches, the encoder 106 may provide the graphic tobe distributed to computing device B 104. In some approaches, theencoder 106 may provide the graphic to a printer to be produced in atangible medium. The encoder 106 may also provide the graphic tocommunications module A 114 for transmission to another device, forexample through email or displayed on a web page.

In some implementations, the encoder 106 generates 204 the graphic andencodes the access information 110. In other implementations, anothercomputing device generates 204 the graphic and sends the graphic tocomputing device A 102. In some implementations, this other computingdevice may be termed a management console and/or may access a managementconsole on computing device A 102 that manages other computing devices(e.g., computing device B 104). The management console may obtain aplug-in that allows it to generate a graphic and store the accessinformation 110 to the graphic. The management console may obtain thisplug-in from computing device A 102 (e.g., an administrative server). Inthese examples, the access information 110 may be stored on computingdevice A 102 (e.g., the administrative server) and sent to themanagement console to incorporate into the graphic, and/or the accessinformation 110 may be stored on the management console to beincorporated into the graphic.

The request receiver 108 receives 206 a configuration informationrequest associated with the graphic. Included is a request to sendconfiguration information B 132 to computing device B 104. In someimplementations, the request may also include technical characteristicsof computing device B. In this example, the technical characteristicsmay be used to determine what portion of configuration information A 112to send to computing device B 104 as configuration information B 132.For example, the request may indicate that an outdated version of asoftware application exists on computing device B 104. As a result,configuration information A 112 relating to an update of that softwareapplication may be sent to computing device B 104 as configurationinformation B 132. Other examples of configuration information A 112include data, network connectivity settings, internet protocols,communication protocols, policies and applications.

In some implementations, the request may be based on input. Drawing fromthe example above, computing device B 104 may further request an updateto an optional video card driver. Thus, the video card driver update maybe included in configuration information A 112 that is sent to computingdevice B 104 as configuration information B 132.

The request may be based on the format of configuration information A112 to be sent. For example, computing device A 102 may includealphanumeric configuration information A 112 within the graphic. Therequest in this example may then include alphanumeric configurationinformation A 112 associated with the graphic, while numericconfiguration information A 112 stored on the graphic is not included.

Computing device A 102 sends 208 configuration information B 132. Oncethe request has been received, and pertinent configuration information B132 compiled, configuration information B 132 is then sent to computingdevice B 104. Configuration information B 132 may be sent over thenetwork 118. Configuration information B 132 may include a portion ofconfiguration information A 112 stored on computing device A 102. Forexample, computing device B 104 may only require configurationinformation B 132 relating to licensing protocols and certaincommunications policies, while configuration information A 112 stored oncomputing device A 102 includes software applications updates. Thus, asubset of configuration information A 112 is sent to computing device B104. In some implementations, computing device A 102 may performadditional or alternative operations in order to secure theconfiguration information. For example, computing device A 102 mayencrypt the configuration information.

In some implementations, sending 208 configuration information B 132 mayinclude obtaining configuration information A 112 from another computingdevice. For example, computing device A 102 (e.g., an administrativeserver) may first obtain configuration information A 112 from amanagement console before sending 208 configuration information B 132 onto computing device B 104.

FIG. 3 is a flow diagram illustrating one configuration of a method 300for receiving configuration information by a computing device. Thegraphic scanner 120 scans 302 a graphic. The graphic may include theaccess information 110. As described above, the access information 110may include one or more pieces of information that allow communicationbetween computing devices on the network 118. An example of accessinformation 110 is the SSID and passkey to the network 118. In oneexample, the graphic may include a portion of the access information110. For example, the SSID of the network 118 may be embedded in thegraphic. In this example, the passkey may be obtained by other means.

Scanning 302 the graphic may include recording and storing the graphicon computing device B 104. For example, the graphic scanner 120 (e.g.,the camera of a smartphone), may take a picture of the graphic and storethe graphic to storage device B 130. If the graphic is printed on aphysical medium, the graphic scanner 120 may convert the physicalgraphic into a digital graphic. Examples of graphic scanners 120include, but are not limited to, cameras, lasers, light sources, CCDscanners and CIS scanners.

In some implementations, the graphic scanner 120 may receive a directiveto scan a graphic. This directive may include activating the graphicscanner 120. In some implementations, the graphic scanner 120 may havean input interface that activates the scan. For example, a graphicscanner 120 (e.g., smartphone camera) may include a button that, whenpressed, takes a picture of the graphic. In another example, asmartphone application, when selected, scans a QR code. In otherimplementations, the graphic scanner 120 is activated without any input.For example, a smartphone application may automatically scan a QR code.

The graphic reader 124 may then extract 304 the access information 110based on the graphic. As explained above, the graphic may contain theaccess information 110 that allows communication over the network 118.The access information 110 may include such things as the network's 118SSID and passkey. The access information 110 may also include the IPaddress of computing device A 102 (e.g., a server). Upon extraction, theaccess information 110 may be implemented to send a configurationinformation request across the network 118. An example of extraction ofthe access information is presented as follows. A graphic reader 124 mayextract the access information 110 (e.g., a URL) that is embedded in aQR code that was scanned by a graphic scanner 120 (e.g., a smartphonecamera). The graphic reader 124 may employ any number of decodingprotocols to extract the information.

In some implementations, extracting 304 the access information 110 mayinclude extracting a portion of the access information 110 stored on thegraphic. For example, numeric access information 110 and alphanumericaccess information 110 may be encoded to the graphic. The graphic reader124 may extract the numeric access information 110 while not extractingthe alphanumeric access information 110. Extraction of a portion of theaccess information 110 may also be determined based on input. Forexample, the access information 110 may include a prompt whereincomputing device B 104 selects the access information 110 to extract.Additionally or alternatively, a portion of the information encoded inthe graphic may be encrypted while another portion is unencrypted. Insome cases, computing device B 104 may initially extract unencryptedaccess information 110 and/or may later extract the encryptedinformation when decryption information (e.g., a decryption key) isprovided by computing device A 102 (upon completing authenticationprocedures, for example).

In some implementations, computing device B 104 may perform additionalor alternative operations in order to access secure communications. Forexample, computing device B 104 may apply an algorithm to decryptencrypted access information 110. In another example, computing device B104 may require entry of a password before access to the network 118 maybe granted.

Computing device B 104 may store the extracted access information 110 tostorage device B 130. As described above, storage device B 130 may beconnected to computing device B 104. In some implementations, storagedevice B 130 may be coupled to computing device B 104 through anintervening computing device.

Computing device B 104 may apply 306 the access information 110 to oneor more communications settings 128. As described above, communicationssettings 128 may establish the procedures and protocols by whichcomputing device B 104 communicates with other computing devices on thenetwork 118 (e.g., computing device A 102). With the access information110 extracted, it may be applied to the communications settings 128 toallow computing device B 104 to communicate across the network 118. Forexample, the SSID and passkey of the network 118 may be incorporatedinto computing device B's 104 communications module B 126 such that thenetwork 118 may be accessed. Applying 306 the access information 110 mayinclude granting computing device B 104 access to the network 118without any input.

In some implementations, computing device B 104 alters the communicationsettings 128 based on the access information 110 to enablecommunications with the network 118. For example, computing device B 104may implement communications protocols and update communicationsdrivers.

The request generator 122 may send 308 a configuration informationrequest associated with the graphic. Once the access information 110 hasbeen applied to the communications settings 128, a configurationinformation request is sent requesting configuration information B 132be sent to computing device B 104. As described above, configurationinformation B 132 may represent information that establishes devicesettings related to computing device B 104. For example, configurationinformation B 132 may include device network settings that allowcommunication between computing devices on the network 118. Otherexamples of configuration information B 132 include, but is not limitedto, network connectivity settings, internet protocols, communicationprotocols, computing policies and applications. Other examples ofconfiguration information will be described in greater detail below.

The request generator 122 may base the configuration information requeston characteristics pertaining to computing device B 104. For example,the request generator 122 may include its system characteristics in theconfiguration information request. Computing device A 102 may then sendconfiguration information B 132 that may be based on those systemcharacteristics.

In some implementations, the configuration information request may bebased on the request generator's 122 input. For example, the requestgenerator 122 may request an update to an old version of a softwareapplication on computing device B 104. In another example, the requestgenerator 122 may base the configuration information request on aresponse to a prompt within the access information 110 to request anupdate to a video card driver.

In some implementations, computing device B 104 may perform additionalor alternative operations in order to secure the configurationinformation request. For example, computing device B 104 may encrypt theconfiguration information request. This secures transmissions ofinformation across the network 118 is secured.

Computing device B 104 may receive 310 configuration information B 132.Configuration information B 132 may be received via the network 118. Asdescribed above, configuration information B 132 may representinformation that establishes device settings related to computing deviceB 104 and may be a subset of configuration information A 112. In someimplementations, computing device B 104 may receive configurationinformation B 132 from another computing device. For example, computingdevice A 102 may first send configuration information B 132 to amanagement console before sending configuration information B 132 on tocomputing device B 104.

According to some implementations, configuration information B 132 mayinclude instructions that implement configuration information B 132 tocomputing device B 104. In some implementations, computing device B 104implements configuration information B 132 on computing device B 104without any additional input. In other implementations, computing deviceB 104 implements configuration information B 132 based on receivedinput. For example, an input interface may solicit permission beforeimplementing configuration information B 132 on computing device B 104.

In some implementations, configuration information B 132 that isreceived is not the same as the configuration information requested. Forexample, computing device B 104 may request a software application.However, computing device A 102 may not include the software applicationin configuration information B 132. For example, computing device B 104may not be formatted to operate the software application.

In some implementations, configuration information B 132 may change oneor more of the operational aspects of computing device B 104. Forexample, additional security protocols may be installed on computingdevice B 104. Additionally, versions of software applications may beupdated.

FIG. 4 is a block diagram that illustrates another configuration ofcomputing devices 402, 404 in which systems and methods for sending andreceiving configuration information may be implemented. Examples ofcomputing device A 402 and/or computing device B 404 include, but arenot limited to, desktop computers, laptop computers, servers,supercomputers, tablet devices, cellular phones, smartphones, gamingsystems and any other computing device. It should be noted that whileFIG. 4 depicts two computing devices 402, 404, the systems and methodsdisclosed herein may be applied to any number of computing devices 402,404.

Computing device A 402 may be similar to computing device A 102described previously. Computing device A 402 may include storage deviceA 416, encoder 406, request receiver 408 and/or communications module A414 similar to corresponding elements described above in connection withFIG. 1.

Computing device B 404 may be similar to computing device B 104described previously. Computing device B 404 may include graphic scanner420, request generator 422, graphic reader 424, communications module B426, communications settings 428 and/or storage device B 430 similar tocorresponding elements described above in connection with FIG. 1. Anetwork 418 may couple computing device A 402 and computing device B404. The network 418 may be similar to network 118 described previously.

It should be noted that one or more of the elements depicted as includedwithin computing device A 402, computing device B 404 and/or the network418 may be implemented in hardware, software or a combination of both.For example, the encoder 406 may be implemented in hardware, software ora combination of both.

The encoder 406 may create a graphic that includes information. Asdescribed above, the graphic created by the encoder 406 may be based onthe access information 410. As described above, access information 410may include one or more pieces of information that allow computingdevice B 404 to communicate with computing device A 402 and/or thenetwork 418. Upon reception, the access information 410 may then enablecomputing device B 404 to communicate with computing device A 402 and/orthe network 418. The access information 410 may include accesslimitations imposed on computing device B 404.

Access information 410 may be similar to access information 110described previously. In some implementations, access information 410may include an authentication information request 434, a networkconnectivity module 436, a digital certificate 438, accessidentification information 440, connecting prompts 462 and/or scanningmodule 464.

Computing device A 402 may send an authentication information request434 along with the access information 410 to identify computing device B404. For example, an authentication information request 434 may includea request that computing device B 404 provide its IP address. In someimplementations, access to the network 418 may be based on a response tothe authentication information request 434. For example, computingdevice A 402 may determine whether or not to grant computing device B404 access to the network 418 based on the response to theauthentication information request 434. In this example, if computingdevice B 404 does not respond to the request or returns an invalid IPaddress, computing device A 402 may deny computing device B 404 accessto the network 418. By comparison, if computing device B 404 doesrespond to the request with a valid IP address, computing device A 402may grant computing device B 404 access to the network 418. According tosome implementations, the determination by computing device A 402whether to grant computing device B 404 access to the network 418 may bedone without any input. In other implementations, computing device A 402may base the determination on input. For example, computing device A 402(e.g., through a system administrator) may evaluate the response to theauthentication information request 434 to determine whether to grantcomputing device B 404 access to the network 418.

Access information 410 may include a network connectivity module 436.The network connectivity module 436 may format computing device B 404 toallow communication with computing device A 402 and/or the network 418.For example, the network connectivity module 436 may evaluate theinternet communications protocols of computing device B 404. Then,computing device A 402 may determine if the internet communicationsprotocols of computing device B 404 are compatible with internetcommunications across the network 418. In some implementations, thenetwork connectivity module 436 may elicit modifications to computingdevice B 404. For example, computing device A 402 may alter computingdevice B's 404 communications settings 428 to restrict what types ofdata may be transferred across the network 418.

A digital certificate 438 may be included in the access information 410to secure the transmission of the access information 410. In someimplementations, the digital certificate 438 may encrypt the accessinformation 410. Then upon presentation with a decryption key, computingdevice B 404 may decrypt the access information 410 to receive theaccess information 410 and/or obtain access to the network 418.According to some approaches, the decryption key may be providedseparately from the digital certificate 438. This may increase thesecurity of the transferred access information 410. Implementation ofthe digital certificate 438 may also authenticate the identity ofcomputing device A 402 and/or the network 418.

Access identification information 440 provides computing device B 404with the information to connect to the network 418. An example of accessidentification information 440 includes the SSID and passkey of thenetwork 418. In some implementations, upon receipt of the accessidentification information 440, computing device B 404 may connect tothe network 418 without any input. In another implementation, computingdevice B 404 may access the network 418 based on input, for examplethrough an input interface where the SSID and passkey of the network 418may be entered. According to an example, a portion of the accessidentification information 440 may be presented. For example, the SSIDof the network 418 may be included in the access information 410. Inthis example, the passkey may be obtained by other means. Accessing theSSID and the passkey individually increases the security of the transferof the access information 410.

A connecting prompt 462 may elicit input from computing device B 404associated with granting computing device B 404 access to the network418. For example, a connecting prompt 462 may elicit input fromcomputing device B 404 pertaining to computing device B's 404 connectionspeed. Based on the response to the connecting prompt 462 computingdevice A 402 may modify computing device B's 404 access to the network418. In other implementations, computing device A 402 may determinewhether to grant computing device B 404 access to the network 418 basedon the response to the connecting prompt 462. According to someapproaches, configuration information B 432 may be based on computingdevice B's 404 response to the connecting prompts 462.

A scanning module 464 may scan computing device B 404 to identify anyrisk associated with granting computing device B 404 access to thenetwork 418. For example, the scanning module 464 may identify a viruson computing device B 404, that may upload to the network 418 ifcomputing device B 404 connects to the network 418. Based on the resultsof the scanning module 464 scan, computing device A 402 may restrictcomputing device B's 404 access to the network 418. In someimplementations, computing device A 402 may not grant computing device B404 access to the network 418. In another implementation, computingdevice A 402 may grant computing device B 404, less than full access tothe network 418. In some implementations, the scanning module 464 may beincluded on another computing device. In these implementations, theother computing device may communicate the results of the scan tocomputing device A 402, wherein computing device A 402 may determine anyaccess limitations imposed on computing device B 404.

Configuration information A 412 may be utilized to configure computingdevices connected to the network 418. Configuration information A 412may be similar to configuration information A 112 described previously.In some implementations, configuration information A 412 may includeauthentication rules A 444 a, configuration identification information A446 a, policies A 448 a, applications A 450 a, settings A 452 a, requestfor inventory data A 454 a, implementation instructions A 466 a, and/orconfiguration prompts A 468 a.

Authentication rules A 444 a, may establish identification standardsassociated with the network 418. For example, the authentication rules A444 a may require that computing devices on the network 418 providetheir IP addresses before using a particular software application. Thismay ensure that any communication between computing device B 404 andcomputing device A 402 and/or the network 418 is authorized. Otherexamples of authentication rules A 444 a include, but are not limitedto, broadcast of identification information to the network 418, trackinghistories of each computing device on the network 418, licensinginformation associated with applications present on the network 418and/or communications authentication protocols associated with thenetwork 418.

Configuration identification information A 446 a may indicateidentification information associated with the network 418. For example,the configuration identification information A 446 a may indicate whatpolicies A 448 a and applications A 450 a are present on the network418. Other examples of configuration identification information A 446 ainclude, but are not limited to, number and/or identification of thecomputing devices on the network 418, system characteristics of thecomputing devices on the network 418, system characteristics of thenetwork 418, identification of subnets within the network 418, memoryusage of the computing devices and/or the network 418, and/or data usageassociated with the network 418.

Policies A 448 a may establish operating standards across the network418. Examples of policies A 448 a include, but are not limited tocommunications protocols, for example restricting email communicationsto particular domains, restricting file types that may be transferred,and/or internet browsing restrictions; maintenance schedules; datastorage allocations; power conservation procedures; anti-virus softwareimplementation; and/or computer tracking procedures such as keyloggingor browsing history storage.

Applications A 450 a may include a set of instructions designed toperform a specified task on a computing device of the network 418. Insome implementations, computing device B 404 may access and implementdifferent applications B 450 b associated with computing device A 402and/or the network 418. Examples of applications A 450 a include, butare not limited to, word processing programs, video editing programs,graphic design programs, desktop publishing programs, video conferencingprograms, games, operating systems, human resources programs and/or dataanalysis programs.

According to some implementations, the applications A 450 a may beincluded on computing device A 402. In other implementations, computingdevice A 402 may be an administrative server that identifiesapplications A 450 a from another computing device (not shown in FIG. 4)on the network 418. In this example, the administrative server mayidentify an application A 450 a located on the other computing deviceand relay all or part of the application A 450 a to computing device B404 as application B 450 b. In this implementation, licensinginformation associated with the applications A 450 a may also beincluded in configuration information A 412. In some implementations,this other computing device may be termed a management console and/ormay access a management console on computing device A 402 that managesother computing devices (e.g., computing device B 404).

Settings A 452 a may alter computing devices on the network 418 suchthat configuration information may be implemented. In someimplementations, settings B 452 b may alter computing device B 404 suchthat configuration information B 432 may be implemented on computingdevice B 404. For example, the settings B 452 b may update computingdevice B's 404 video card driver to allow a video conferencingapplication B 450 b to be implemented on computing device B 404.

A request for inventory data A 454 a may direct computing devices on thenetwork 418 to send inventory data to computing device A 402. Forexample, request for inventory data B 454 b may request that computingdevice B 404 sends inventory data 460 to computing device A 402 and/orthe network 418. From this inventory data request B 454 b, computingdevice A 402 may obtain information from computing device B 404associated with its system characteristics. Computing device A 402 maystore this information on storage device A 416.

Implementation instructions A 466 a may instruct computing devices onthe network 418 how to implement configuration information. In someapproaches, implementation instructions B 466 b may direct computingdevice B 404 to restart at various intervals while implementingconfiguration information B 432. In other approaches, the implementationinstructions B 466 b may indicate the order in which to implementconfiguration information B 432. For example, the implementationinstructions B 466 b may indicate that an update to an operating systembe implemented before a video card driver is installed.

Configuration prompts A 468 a may elicit input from computing devices onthe network 418 during implementation of configuration information. Forexample, configuration prompt B 468 b may elicit input from computingdevice B 404 during implementation of configuration information B 432.In some approaches, configuration prompts B 468 b may include a requestfor selection between optional applications B 450 b to be implemented.For example, a configuration prompt B 468 b may elicit a selectionbetween two Wi-Fi configurations to be implemented on computing device B404. Based on the selection, configuration information B 432 wouldincorporate the corresponding Wi-Fi configuration.

Communications module A 414 allows computing device A 402 to communicatewith other computing devices on network 418. Communications module A 414may set standards for communication between computing device A 402 andcomputing device B 404. Communications module A 414 may also includecertain restrictions on communications.

The request receiver 408 receives requests for configuration informationfrom computing device B 404. The request received by the requestreceiver 408 may include information relating to computing device B 404.Based on the request, the request receiver 408 may then determinerelated configuration information A 412. Additionally or alternatively,the request receiver 408 may determine pertinent configurationinformation A 412 based on input. In some implementations, the requestreceiver 408 may require authentication information 458 beforeprocessing a request.

Computing device A 402 may send all or part of configuration informationA 412 to computing device B 404. Computing device B 404 may receiveconfiguration information B 432 (which may be all or part ofconfiguration information A 412, for example) from computing device A402. In some implementations, computing device A 402 may be anadministrative server that receives configuration information A 412 fromanother computing device (not shown in FIG. 4). In this example, theadministrative server may receive configuration information A 412 fromthe other computing device and relay all or part of configurationinformation A 412 to computing device B 404. In some implementations,this other computing device may be termed a management console and/ormay access a management console on computing device A 402 that managesother computing devices (e.g., computing device B 404).

In some implementations, security module A 442 may perform additional oralternative operations in order to secure communications. For example,security module A 442 may encrypt configuration information B 432. Inanother example, security module A 442 may implement a spread spectrumto transfer configuration information B 432 using a radio frequencysignal to further secure configuration information B 432. In otherexamples, security module A 442 may create a password interface toaccompany configuration information B 432, such that entry of a passwordis required before configuration information B 432 may be implemented.

Computing device A 402 may be coupled to computing device B 404 througha network 418 similar to the network 118 described previously. Examplesof network 418 include personal area networks, local area networks, widearea networks, cellular networks and any other type of network.

The graphic scanner 420 records and stores the graphic to computingdevice B 404. In some implementations, a graphic reader 424 may becoupled to the graphic scanner 420. The graphic reader 424 may extractthe information stored within the graphic. The graphic reader 424 mayemploy any number of decoding protocols to extract the information.

The request generator 422 may send a request to computing device A 402to obtain configuration information B 432. The request sent by therequest generator 422 may include information relating to computingdevice B 404. The request generator 422 may base the request on thecharacteristics of computing device B 404. The request generator 422 mayalso base the request on input.

Computing device B 404 may also include a communications module B 426that allows computing device B 404 to communicate with computing deviceA 402 and/or the network 418. Communications settings 428 withincommunications module B 426 may establish the procedure by whichcomputing device B 404 communicates with computing device A 402 and/orthe network 418.

Computing device B 404 may receive configuration information B 432.Configuration information B 432 may represent information thatestablishes device settings related to computing device B 404. In someimplementations, configuration information B 432 may constitute aportion of configuration information A 412. For example, as describedabove configuration information A 412 may include authentication rules A444 a, configuration identification information A 446 a, policies A 448a, applications A 450 a, settings A 452 a, request for inventory data A454 a, implementation instructions A 466 a, and/or configuration promptsA 468 a. In this example configuration information B 432 may include aportion of any and/or all of these elements. For example, configurationinformation B 432 may include authentication rules B 444 b,configuration identification information B 446 b, policies B 448 b,applications B 450 b, settings B 452 b, request for inventory data B 454b, implementation instructions B 466 b and/or configuration prompts B468 b. More particularly, configuration information A 412 may includepolicies A 448 a relating to power management and scheduled maintenance.In this example, configuration information B 432 may include policies B448 b relating to power management, while scheduled maintenance policesare not included. It should be noted that the pieces of configurationinformation A 412 corresponding to the pieces of configurationinformation B 432 may include the same or different amounts ofinformation. For example, policies B 448 b may be a subset or supersetof policies A 448 a.

In some implementations, the portion of configuration information A 412included in configuration information B 432 may be associated with thedevice settings of computing device B 404. Computing device A 402 maysend all or part of configuration information A 412 to computing deviceB 404. Computing device B 404 may receive configuration information B432 (which may be all or part of configuration information A 412, forexample) from computing device A 402.

In some implementations, security module B 456 may perform additional oralternative operations in order to access secure communications. Forexample, security module B 456 may decrypt configuration information B432. In another example, security module B 456 may identify a bandwidthover which configuration information B 432 is transferred to extractconfiguration information B 432 from a spread spectrum. In otherexamples, the security module B 456 may include a password inputinterface to access configuration information B 432.

Authentication information 458 associated with computing device B 404may identify computing device B 404 to computing device A 402 and/or thenetwork 418. As described above, computing device A 402 may use theauthentication information 458 to determine what, if any, level ofaccess to the network 418 computing device B 404 is granted. Forexample, computing device A 402 may grant a mobile device less networkaccess than a desktop computer. In this example, computing device A 402may use the authentication information 458 associated with eachcomputing device to grant an appropriate level of access to the network418. Examples of authentication information 458 include, but are notlimited to, username, password, biometric information, IP address, MediaAccess Control (MAC) address and device name verification.

Inventory data 460 associated with computing device B 404 may beincluded in computing device B 404. Examples of inventory data 460include, but are not limited to, hardware inventory, software inventory,data inventory, network inventory and/or usage inventory. In someimplementations, the inventory data 460 may be sent to computing deviceA 402 and/or the network 418. In these implementations computing deviceA 402 may implement the inventory data 460 to manage the computingdevices on the network 418.

FIG. 5 is a flow diagram illustrating another configuration of a method500 for sending configuration information by a computing device.Computing device A 402 obtains 502 access information 410. In someimplementations, this may be done as described in connection with FIG.2. As described above, the access information 410 may include one ormore pieces of information that allows communication between computingdevices on the network 418.

The encoder 406 may generate 504 a graphic based on the accessinformation 410. The access information 410 may be embedded in thegraphic. In some implementations, this may be done as described inconnection with FIG. 2.

If the access information 410 includes an authentication informationrequest 434, computing device A 402 receives 506 the authenticationinformation 458. Authentication information 458 associated withcomputing device B 404 may identify computing device B 404 to computingdevice A 402 and/or the network 418. For example, in this step computingdevice A 402 may receive the IP address of computing device B 404. Insome implementations, computing device A 402 may be an administrativeserver that sends the authentication information 458 to anothercomputing device. In this example, the administrative server may receiveauthentication information 458 from computing device B 404 and relay allor part of the authentication information 458 to the other computingdevice. In some implementations, this other computing device may betermed a management console and/or may access a management console oncomputing device A 402 that manages other computing devices (e.g.,computing device B 404).

Based on the validity of the authentication information 458, computingdevice A 402 may determine what, if any, level of network access togrant computing device B 404. For example, if computing device A 402receives invalid authentication information 458 (e.g., an invalid IPaddress), computing device A 402 may deny network access. In thisexample, computing device A 402 may deny a configuration informationrequest sent by computing device B 404.

According to some implementations, computing device A's 402determination of whether to grant computing device B 404 access to thenetwork may be done without any input. In other implementations,computing device A 402 may base the determination on input. For example,computing device A 402 (e.g., through a system administrator) mayevaluate the received authentication information 458 to determine what,if any, access to grant to computing device B 404.

In other implementations, computing device A 402 may apply the receivedauthentication information 458 to determine what configurationinformation B 432 is sent to computing device B 404. For example,computing device A 402 may include Wi-Fi configuration information A 412for a tablet. Computing device A 402 may use the authenticationinformation 458 received from with computing device B 404 (e.g. atablet) to determine that the Wi-Fi configuration information A 412should be sent to computing device B 404.

The request receiver 408 receives 508 a configuration informationrequest associated with the graphic. In some implementations, this maybe done as described in connection with FIG. 2. Included is a request tosend configuration information B 432 to computing device B 404.

Security module A 442 secures 510 configuration information B 432 toproduce secured configuration information B 432. In someimplementations, security module A 442 may perform additional oralternative operations in order to secure communications. For example,security module A 442 may encrypt configuration information B 432.Security module A 442 may use any number of encryption techniques tosecure configuration information B 432. In another example, securitymodule A 442 may associate a password with configuration information B432 such that computing device B 404 may input the password beforeaccessing configuration information B 432. In some approaches, computingdevice A 402 may provide computing device B 404 with the password toaccess configuration information B 432. Securing configurationinformation B 432 in this fashion increases the security ofcommunications over the network 118.

Computing device A 402 sends 512 configuration information B 432. Insome implementations, this may be done as described in FIG. 2.Configuration information B 432 may include a portion of configurationinformation A 412 stored on computing device A 402. In someimplementations, sending configuration information B 432 may includeobtaining configuration information B 432 from another computing device.For example, computing device A 402 (e.g., an administrative server) mayfirst obtain configuration information A 412 from a management consolebefore sending configuration information B 432 on to computing device B404.

Computing device A 402 may send 514 an inventory data request tocomputing device B 404. In this request computing device A 402 mayinstruct computing device B 404 to determine inventory data 460 and sendthe inventory data 460 to computing device A 402 and/or the network 418.In some implementations computing device A 402 may store the inventorydata 460 to storage device A 416. Computing device A 402 may furtherimplement this inventory data 460 to manage computing devices on thenetwork 418. In some implementations, the request may be based onauthentication information 458. For example, after receivingauthentication information 458 that identifies computing device B 404 asa smart phone, computing device A 402 may send a cellular networkinventory data request. Furthermore, in this example, a request forinventory data pertaining to audio peripherals is not necessary, and asa result may not be sent.

In some implementations, computing device A 402 may also send a prompteliciting a selection of what, if any, inventory data 460 to send tocomputing device A 402 and/or the network 418. For example, theinventory data request may include a prompt to elicit selection ofwhether to determine and send inventory data associated with computingdevice B's 404 operating system. In some implementations, access to thenetwork 118 may be based on the response to the prompt. For example, ifcomputing device B 404 elects not to send the operating system inventorydata, computing device A 402 may terminate or otherwise restrictcomputing device B's 404 access to the network 418.

Computing device A 402 may also receive 516 inventory data 460.Computing device A 402 may implement this inventory data 460 in managingcomputing devices of the network 418. In some implementations, theinventory data 460 requested is not the same as the inventory data 460received. For example, computing device B 404 may have elected to send aportion of the inventory data 460 requested. In this example, computingdevice A 402 may terminate, or otherwise restrict, computing device B's404 access to the network 118. In another example, computing device A402 may send a general inventory data request to computing device B 404(e.g., a desktop computer) that includes a request for cellular usageinventory data 460. In this example, a desktop computer does not use acellular network and therefore does not send information associated withthis request. Thus, the inventory data 460 received does not match theinventory data 460 requested.

In this example, computing device a 402 may relay all or part of theinventory data 460 to another computing device. In some implementations,this other computing device may be termed a management console and/ormay access a management console on computing device A 402 that managesother computing devices (e.g., computing device B 404).

FIG. 6 is a flow diagram illustrating another configuration of a method600 for receiving configuration information by a computing device.Computing device B 404 obtains 602 a graphic reader 424 that decodes theaccess information 410. The graphic reader 424 may extract the accessinformation 410 stored within a graphic.

In some implementations, the graphic reader 424 may be obtained fromcomputing device A 402. In other implementations, computing device A 402may be an administrative server that obtains the graphic reader 424 fromanother computing device. In this example, the administrative server mayobtain the graphic reader 424 from the other computing device and relayall or part of the graphic reader 424 to computing device B 404. In someimplementations, the other computing device may be the manufacturer ofcomputing device B 404 and/or the manufacturer of the graphic reader424. In other implementations, this other computing device may be termeda management console and/or may access a management console on computingdevice A 402 that manages other computing devices (e.g., computingdevice B 404). In other implementations, this other computing device maybe computing device B's 404 manufacturer.

In other implementations, computing device B 404 may obtain the graphicreader 424 from another computing device. In these implementations, thegraphic reader 424 may be included with computing device B 404 or may beobtained separately from computing device B 404. For example, thegraphic reader 424 could be downloaded from a website associated withthe other computing device. In some implementations, this othercomputing device may be computing device B's 404 manufacturer.

Computing device B 404 may obtain 604 a security module that interpretssecured configuration information B 432. As described above, securitymodule A 442 may perform additional or alternative operations in orderto secure communications. To interpret this secured configurationinformation, computing device B 404 may obtain a security module B 456which may perform additional or alternative operations in order toaccess the secured configuration information.

In some implementations, computing device B 404 may obtain 604 thesecurity module B 456 from computing device A 402. In otherimplementations, computing device A 402 may be an administrative serverthat obtains the security module B 456 from another computing device. Inthis example, the administrative server may obtain the security module B456 from the other computing device and relay all or part of thesecurity module B 456 to computing device B 404. In someimplementations, the other computing device may be the manufacturer ofcomputing device B 404 and/or the manufacturer of the graphic reader424. In other implementations, this other computing device may be termeda management console and/or may access a management console on computingdevice A 402 that manages other computing devices (e.g., computingdevice B 404). In other implementations, this other computing device maybe computing device B's 404 manufacturer.

In other implementations, computing device B 404 may obtain 604 thesecurity module B 456 from another computing device. In theseimplementations, the security module B 456 may be included withcomputing device B 404 or may be obtained separately from computingdevice B 404. For example, the security module 456 could be downloadedfrom a website associated with the other computing device. In someimplementations, this other computing device may be computing device B's404 manufacturer.

The graphic scanner 420 scans 606 a graphic. In some implementations,this may be done as described in connection with FIG. 3. As describedabove, the graphic may contain the access information 410.

The graphic reader 424 may then extract 608 the access information 410based on the graphic. In some implementations, this may be done asdescribed in connection with FIG. 3. As explained above, the graphiccontains the access information 410 that allows communication over thenetwork 418. Upon extraction, the access information 410 may be used tosend a configuration information request across the network 418. In someimplementations, security module B 456 may perform additional oralternative operations in order to access secure communications. Forexample, security module B 456 may apply an algorithm to decryptencrypted access information 410. In another example, security module B456 may require entry of a password before access to the network 418 maybe granted.

Computing device B 104 may apply 610 the access information 410 to thecommunications settings 428. In some implementations, this may be doneas described in connection with FIG. 3. As described above,communications settings 428 may establish the procedures and protocolsby which computing device B 404 communicates with other computingdevices on the network 418 (e.g., computing device A 402).

Computing device B 404 may send 612 authentication information 458. Insome implementations, computing device B 404 sends the authenticationinformation 458 in response to an authentication information request 434b. The authentication information 458 may identify computing device B404 to computing device A 402 and/or the network 418. For example, theauthentication information 458 may include computing device B's 404 MACaddress. In some implementations, computing device B 404 sends theauthentication information 458 to computing device A 402 and/or thenetwork 418. Whether or not computing device B 404 receivesconfiguration information B 432 may be based on the authenticationinformation 458 sent to computing device A 402. For example, computingdevice B 404 may send invalid authentication information 458, which mayresult in no configuration information B 432, or a limited portion ofconfiguration information B 432, being received.

In some implementations, computing device B 404 sends the authenticationinformation 458 without input. For example, upon applying the accessinformation 410, computing device B 404 may send the authenticationinformation 458 without input. In another example, computing device B404 may require input before sending the authentication information 458.

The request generator 422 may send 614 a configuration informationrequest associated with the graphic. In some implementations, this maybe done as described in connection with FIG. 3. As described above,configuration information B 432 may represent information thatestablishes device settings related to computing device B 404. In someimplementations, security module B 456 may perform additional oralternative operations in order to access secured configurationinformation B 432.

Computing device B 404 may receive 616 configuration information B 432.In some implementations, this may be done as described in connectionwith FIG. 3. As described above, configuration information B 432 mayrepresent information that establishes device settings related tocomputing device B 404 and may be a subset of configuration informationA 412. In some implementations, configuration information B 432 that isreceived is not the same as the configuration information requested.

Computing device B 404 may determine 618 inventory data 460. Computingdevice B 404 may include inventory data 460 that describes its systemcharacteristics. As described above, computing device B 404 may includeinventory data 460. Examples of inventory data 460 include, but are notlimited to, hardware inventory, software inventory, data inventory,network inventory and/or usage inventory. In some implementations,computing device B 404 determines its inventory data 460 without anyinput. In other implementations, inventory data 460 is determined basedon input. For example, computing device B 404 may include a prompt thatupon selection determines the inventory data 460.

Computing device B 404 may send 620 the inventory data 460 to computingdevice A 402 and/or the network 418. In some approaches, computingdevice B 404 may send the inventory data 460 in response to an inventorydata request. The inventory data 460 may be implemented by computingdevice A 402 and/or the network 418 to manage computing devices on thenetwork 418. In some implementations, computing device B 404 may sendthe inventory data without any input. For example, upon receipt of aninventory data request, computing device B 404 may automatically sendthe inventory data 460. In other implementations, computing device B 404may require input before sending the inventory data 460.

FIG. 7 is a thread diagram illustrating one configuration of computingdevice A 702 and computing device B 704 sending and receivingconfiguration information. Computing device A 702 obtains 706 accessinformation 410. In some implementations, this may be done as describedin connection with FIG. 2. As described above, the access information410 may include one or more pieces of information that allowscommunication between computing devices on the network 418.

Computing device A 702 generates 708 a graphic based on the accessinformation 410. In some implementations, this may be done as describedin connection with FIG. 2. The access information 410 may be embedded inthe graphic.

Computing device B 704 obtains 710 a graphic reader 424 that decodes theaccess information 410. In some implementations, this may be done asdescribed in connection with FIG. 6. The graphic reader 424 may extractthe access information stored with a graphic.

Computing device B 704 may obtain 712 a security module B 456 thatinterprets secured configuration information B 432. In someimplementations, this may be done as described in FIG. 6. In someimplementations, security module B 456 may perform additional oralternative operations in order to access secure communications.

Computing device B 704 scans 714 a graphic generated by computing deviceA 702. In some implementations, this may be done as described inconnection with FIG. 3. As described above, the graphic may contain theaccess information 410.

Upon receipt of the graphic, computing device B 704 may then extract 716the access information 410 based on the graphic. In someimplementations, this may be done as described in connection with FIG.3. As explained above, the graphic contains the access information 410that allows computing device B 704 to communicate with computing deviceA 702 and/or the network 418.

Computing device B 704 may apply 718 the access information 110 to thecommunications settings 428. In some implementations, this may be doneas described in connection with FIG. 3. As described above,communications settings 428 may establish the procedures and protocolsby which computing device B 704 communicates with other computingdevices on the network 418.

If the access information 410 included an authentication informationrequest 434 b, computing device B 704 may send 720 authenticationinformation 458 to computing device A 702. In some implementations, thismay be done as described in connection with FIGS. 5 and 6. Theauthentication information 458 may identify computing device B 704 tocomputing device A 702 and/or the network 418.

After applying the access information 410, computing device B 704 maysend 722 a configuration information request associated with the graphicto computing device A 702. In some implementations, this may be done asdescribed in connection with FIGS. 2 and 3. As described above, includedis a request to send configuration information B 432 to computing deviceB 704.

Computing device A 702 may secure 724 configuration information B 432 toproduce secured configuration information B 432. In someimplementations, this may be done as described in FIG. 5. Securingconfiguration information B 432 in this fashion increases the securityof communications over the network 418.

Computing device A 702 may send 726 configuration information B 432 tocomputing device B 704. In some implementations, this may be done asdescribed in FIGS. 2 and 3. Configuration information B 432 may includea portion of configuration information A 412 stored on computing deviceA 702.

Computing device A 702 may send 728 an inventory data request tocomputing device B 704. In some implementations, this may be done asdescribed in FIG. 5. In this request computing device A 702 may instructcomputing device B 704 to send inventory data 460 to computing device A702 and/or the network 418.

Computing device B 704 may determine 730 inventory data 460. In someimplementations, this may be done as described in FIG. 6. In someimplementations computing device B 704 may determine inventory data 460in response to an inventory data request sent by computing device A 702.

After collecting the inventory data, computing device B 704 may send 732the inventory data to computing device A 702. In some implementations,this may be done as described in FIGS. 5 and 6.

FIG. 8 is a block diagram that illustrates one configuration of anadministrative system 802 and a managed node 804, in which systems andmethods for sending and receiving configuration information may beimplemented. It should be noted, that while FIG. 8 depicts one managednode 804, any number of managed nodes 804 may be present.

The administrative system 802 may include a management application 870,storage device A 816 and/or encoder 806 similar to correspondingelements described above in connection with FIG. 4. Managed node 804 mayinclude authentication information 858, graphic scanner 820, requestgenerator 822, graphic reader 824, communications module B 826,communications settings 828, inventory data 860, security module B 856and/or storage device B 830 similar to corresponding elements describedabove in connection with FIG. 4. In some instances the administrativesystem 802 may communicate with the managed node 804 via a network 818similar to the network 118 described previously.

It should be noted that one or more of the elements depicted as includedwithin administrative system 802 and/or managed node 804 may beimplemented in hardware, software or a combination of both. For example,the encoder 806 may be implemented in hardware, software or acombination of both.

The administrative system 802 implements the management application 870to oversee managed node 804. In some implementations, the managementapplication 870 includes a request receiver 808, security module A 842,access information 810 and/or configuration information A 812 similar tocorresponding elements described above in connection with FIG. 4. Insome implementations, the access information 810 incorporated in themanagement application 870 may include authentication informationrequest 834, a network connectivity module 836, a digital certificate838, access identification information 840, connecting prompts 862and/or a scanning module 864 similar to corresponding elements describedabove in connection with FIG. 4.

Additionally, in some implementations, configuration information A 812incorporated in the management application 870 may includeauthentication rules A 844 a, configuration identification information A846 a, policies A 848 a, applications A 850 a, settings A 852 a, requestfor inventory data A 854 a, implementation instructions A 866 a and/orconfiguration prompts A 868 a similar to corresponding elementsdescribed above in connection with FIG. 4. In some approaches,configuration information B 832 may include authentication rules B 844b, configuration information B 846 b, policies B 848 b, applications B850 b, settings B 852 b, request for inventory data B 854 b,implementation instructions B 866 b and/or configuration prompts B 868 bsimilar to corresponding elements described above in connection withFIG. 4.

In some implementations, configuration information B 832 may include anagent 872. The agent 872 establishes a connection between theadministrative system 802 and the managed node 804 wherein theadministrative system 802 has some control over the managed node 804.For example, the agent 872 may permit the administrative system 802 toremotely control operational aspects of the managed node 804. Otherexamples of functions of the agent 872 include, but are not limited to,running diagnostic tests on the managed node 804, installing devicedrivers and/or applications 850 b on the managed node 804, scanning formalware on the managed node 804, sending reports to the administrativesystem 802, prohibiting unauthorized use (e.g., prohibit softwareinstallations, prohibit browsing) on the managed node 804, relayinginformation to the administrative system 802, managing license usage bythe managed node 804, managing power conservation on the managed node804, directing certain activities (e.g., what software is running) onthe managed node 804, and/or perform maintenance and/or repairs to themanaged node 804.

FIG. 9 is a block diagram that illustrates one configuration of anetwork where systems and methods for sending and receivingconfiguration information may be implemented. A computing device 902 isconnected to a router 974. In FIG. 9, the computing device 902 may beone example of one or more of the computing devices 102, 402, 702 andadministrative system 802 described above. The router 974 is connectedto switches 976 a, 976 b and 976 c. Switch 976 a is connected to severalnodes 978 a, 978 b, 978 c, etc., via their respective subnets 980 a, 980b and 980 c. The switch 976 b is connected to several nodes 978 d, 978e, 978 f etc., via their respective subnets 980 d, 980 e and 980 f. Theswitch 976 c is connected to several nodes 978 g, 978 h, 978 i, etc.,via their respective subnets 980 g, 980 h, 980 i. In FIG. 9, a node 978may be one example of one or more of the computing devices 104, 404, 704and managed node 804 described above. Although FIG. 9 only shows onerouter 974, and a limited number of switches 976, subnets 980 and nodes978, many and varied numbers of routers 974 switches 976, subnets 980,and nodes 978 may be included in networks and/or systems where systemsand methods for determining differences between file system contents maybe implemented.

FIG. 10 illustrates various components that may be utilized on acomputing device 1082. One or more of the computing devices 102, 102,402, 404 702, 704, 902, administrative system 802, managed node 804 andnodes 978 described above may be implemented in accordance with thecomputing device 1082 illustrated in FIG. 10. For example, the computingdevice 1082 may be configured to perform one or more of the methods 200,300, 500, 600 described above. The illustrated components may be locatedwithin the same physical structure or in separate housings orstructures.

The computing device 1082 may include a processor 1084 and memory 1086.The processor 1084 controls the operation of the computing device 1082and may be embodied as a microprocessor, a microcontroller, a digitalsignal processor (DSP) or other device known in the art. The memory 1086may include instructions 1088 a and data 1090 a. The processor 1084typically performs logical and arithmetic operations based on programinstructions 1088 a and data 1090 a stored within the memory 1086. Thatis, instructions 1088 b and data 1090 b may be stored and/or run on theprocessor 1084. The instructions 1088 a-b may be executable to performone or more of the methods 200, 300, 500, 600 described above.

The computing device 1082 typically may include one or morecommunication interfaces 1092 for communicating with other electronicdevices. The communication interfaces 1092 may be based on wiredcommunication technology, wireless communication technology, or both.Examples of different types of communication interfaces 1092 include aserial port, a parallel port, a USB, an Ethernet adapter, an IEEE 1394bus interface, a small computer system interface (SCSI) bus interface,an infrared (IR) communication port, a Bluetooth wireless communicationadapter and so forth.

The computing device 1082 typically may include one or more inputdevices 1094 and one or more output devices 1096. Examples of differentkinds of input devices 1094 include a keyboard, mouse, microphone,remote control device, button, joystick, trackball, touchpad, lightpen,etc. Examples of different kinds of output devices 1096 include aspeaker, printer, etc. One specific type of output device that may betypically included in a computer system is a display device 1001.Display devices 1001 used with embodiments disclosed herein may utilizeany suitable image projection technology, such as a cathode ray tube(CRT), liquid crystal display (LCD), light-emitting diode (LED), gasplasma, electroluminescence or the like. A display controller 1003 mayalso be provided for converting data stored in the memory 1086 intotext, graphics and/or moving images (as appropriate) shown on thedisplay device 1001.

Of course, FIG. 10 illustrates only one possible configuration of acomputing device wherein systems and methods for determining a groupbased on a relationship may be performed. Various other architecturesand components may be utilized.

In the above description, reference numbers have sometimes been used inconnection with various terms. Where a term is used in connection with areference number, this is meant to refer to a specific element that isshown in one or more of the Figures. Where a term is used without areference number, this is meant to refer generally to the term withoutlimitation to any particular Figure.

As used herein, the term “close to” and other variations thereof maymean that a low latency link exists between the two devices that are“close to” each other. For example, a low latency link may be a localarea network that may cover a limited geographical area (e.g., home,office, computer laboratory, building, etc.).

As used herein, the term “agent” and other variations thereof may referto software and/or hardware that is/are used to manage and/or performoperations on a managed computing device. For example, the agent mayreceive and perform instructions from an administrative system. Forinstance, the agent may uninstall software, eliminate threats (e.g.,viruses, Trojans, worms, malware, adware, spyware, etc.), reportinformation to the administrative system (e.g., usage reports, status,etc.), update firmware, detect unauthorized use, detect unauthorizedproducts on the managed computing device, etc.

As used herein, the term “coupled” and other variations thereof may meanthat one element is connected to another element directly or indirectly.For example, if a first element is coupled to a second element, thefirst element may be connected directly to the second element or may beconnected to the second element through another element.

The term “determining” encompasses a wide variety of actions and,therefore, “determining” can include calculating, computing, processing,deriving, investigating, looking up (e.g., looking up in a table, adatabase or another data structure), ascertaining and the like. Also,“determining” can include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” can include resolving, selecting, choosing, establishingand the like.

The phrase “based on” does not mean “based only on,” unless expresslyspecified otherwise. In other words, the phrase “based on” describesboth “based only on” and “based at least on.”

The term “processor” should be interpreted broadly to encompass ageneral purpose processor, a central processing unit (CPU), amicroprocessor, a digital signal processor (DSP), a controller, amicrocontroller, a state machine, and so forth. Under somecircumstances, a “processor” may refer to an application specificintegrated circuit (ASIC), a programmable logic device (PLD), a fieldprogrammable gate array (FPGA), etc. The term “processor” may refer to acombination of processing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

The term “memory” should be interpreted broadly to encompass anyelectronic component capable of storing electronic information. The termmemory may refer to various types of processor-readable media such asrandom access memory (RAM), read-only memory (ROM), non-volatile randomaccess memory (NVRAM), programmable read-only memory (PROM), erasableprogrammable read only memory (EPROM), electrically erasable PROM(EEPROM), flash memory, magnetic or optical data storage, registers,etc. Memory is said to be in electronic communication with a processorif the processor can read information from and/or write information tothe memory. Memory that is integral to a processor is in electroniccommunication with the processor.

The terms “instructions” and “code” should be interpreted broadly toinclude any type of computer-readable statement(s). For example, theterms “instructions” and “code” may refer to one or more programs,routines, sub-routines, functions, procedures, etc. “Instructions” and“code” may comprise a single computer-readable statement or manycomputer-readable statements.

The term “computer-readable medium” refers to any available medium thatcan be accessed by a computer or processor. By way of example, and notlimitation, a computer-readable medium may comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to carryor store desired program code in the form of instructions or datastructures and that can be accessed by a computer or processor. Itshould be noted that a computer-readable medium may be non-transitoryand tangible. Disk and disc, as used herein, includes compact disc (CD),laser disc, optical disc, digital versatile disc (DVD), floppy disk andBlu-ray® disc where disks usually reproduce data magnetically, whilediscs reproduce data optically with lasers.

Software or instructions may also be transmitted over a transmissionmedium. For example, if the software is transmitted from a web site,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition oftransmission medium.

The methods disclosed herein comprise one or more steps or actions forachieving the described method(s). The method steps and/or actions maybe interchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isrequired for proper operation of the method that is being described, theorder and/or use of specific steps and/or actions may be modifiedwithout departing from the scope of the claims.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the systems, methods, and apparatus described herein withoutdeparting from the scope of the claims.

What is claimed is:
 1. An apparatus, comprising: a processor of amanagement server; and a memory operatively coupled to the processor,the processor configured to: generate a graphic that encodes informationassociated with the management server, the information including atleast one of an Internet Protocol (IP) address of the management serveror a uniform resource locator (URL) of the management server; providethe graphic to a compute device such that the compute device extractsthe information from the graphic to associate the compute device withthe management server; receive a response from the compute device inresponse to the compute device extracting the information from thegraphic, the response including a request associated with a devicesetting; and associate, based on the response, the compute device withat least one computing policy that changes the device setting of thecompute device.
 2. The apparatus of claim 1, wherein the changes to thedevice setting includes updating a security protocol on the computedevice.
 3. The apparatus of claim 1, wherein the information includesunencrypted information and encrypted information.
 4. The apparatus ofclaim 1, wherein the processor is configured to provide a decryption keyto the compute device to decrypt at least a portion of the informationencoded in the graphic.
 5. The apparatus of claim 1, wherein theprocessor is configured to provide a decryption key to the computedevice to decrypt at least a portion of the information encoded in thegraphic, the processor configured to provide the decryption key to thecompute device separately from providing the graphic to the computedevice.
 6. The apparatus of claim 1, wherein the processor is configuredto provide the graphic to the compute device by sending a representationof the graphic to a printer associated with the compute device.
 7. Theapparatus of claim 1, wherein the processor is configured to provide thegraphic to the compute device by sending a representation of the graphicto the compute device via a network.
 8. The apparatus of claim 1,wherein the processor is configured to provide the graphic to thecompute device via at least one of an email or a web page.
 9. Theapparatus of claim 1, wherein the graphic further encodes configurationinformation.
 10. The apparatus of claim 1, wherein the processor isconfigured to send an inventory request to the compute device inresponse to the response, and receive inventory data from the computedevice based on the inventory request, the computing policy beingselected based on the inventory data.
 11. A method, comprising:generating, at a processor of a management server, a graphic thatencodes information including at least one of a username, an InternetProtocol (IP) address of the management server or a uniform resourcelocator (URL) of the management server; providing, at the processor ofthe management server, the graphic to a managed node such that themanaged node extracts the information from the graphic to associate themanaged node with the management server; receiving, at the processor ofthe management server, a response from the managed node in response tothe managed node extracting the information from the graphic; andassociating, at the processor of the management server and based on theresponse, the managed node with at least one computing policy used toconfigure the managed node.
 12. The method of claim 11, wherein theinformation includes unencrypted information and encrypted information.13. The method of claim 11, further comprising providing a decryptionkey to the managed node to decrypt at least a portion of the informationencoded in the graphic.
 14. The method of claim 11, further comprisingproviding, separately from the providing the graphic to the managednode, a decryption key to the managed node to decrypt at least a portionof the information encoded in the graphic.
 15. The method of claim 11,wherein the providing the graphic to the managed node includes sending arepresentation of the graphic to a printer associated with the managednode.
 16. The method of claim 11, wherein the providing the graphic tothe managed node includes sending a representation of the graphic to themanaged node via a network.
 17. The method of claim 11, wherein theproviding the graphic to the managed node is via at least one of anemail or a web page.
 18. The method of claim 11, wherein the graphicfurther encodes configuration information.
 19. The method of claim 11,further comprising: sending an inventory request to the managed node inresponse to the response; and receiving inventory data from the managednode based on the inventory request, the at least one computing policybeing selected based on the inventory data.
 20. The method of claim 11,wherein the associating the managed node with the at least one computingpolicy changes an operational setting of the managed node.